Communication system

ABSTRACT

A communication system is described in which machine-type communication devices having a reduced bandwidth can be allocated physical uplink control channel resources that fall within that reduced bandwidth whilst other, legacy, devices can continue to use physical uplink control channel resources that do not fall within that reduced bandwidth.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a Continuation application of Ser. No.17/746,259 filed May 17, 2022, which is a Continuation application ofSer. No. 16/885,791 filed on May 28, 2020, which is a Continuationapplication of Ser. No. 15/512,596 filed on Mar. 20, 2017, which isissued as U.S. Pat. No. 10,694,524, which is a National Stage Entry ofPCT/JP2015/004690 filed on Sep. 15, 2015, which claims priority fromUnited Kingdom Patent Application 1416796.9 filed on Sep. 23, 2014, thecontents of all of which are incorporated herein by reference, in theirentirety.

TECHNICAL FIELD

The present invention relates to mobile communications devices andnetworks, particularly but not exclusively those operating according tothe 3^(rd) Generation Partnership Project (3GPP) standards orequivalents or derivatives thereof. The invention has particularalthough not exclusive relevance to the Long Term Evolution (LTE) ofUTRAN (called Evolved Universal Terrestrial Radio Access Network(E-UTRAN)), including LTE-Advanced.

BACKGROUND ART

In a mobile (cellular) communications network, (user) communicationdevices (also known as user equipment (UE), for example mobiletelephones) communicate with remote servers or with other communicationdevices via base stations. In their communication with each other,communication devices and base stations use licensed radio frequencies,which are typically divided into frequency bands and/or time blocks.

In order to be able to communicate via the base stations, communicationdevices need to monitor control channels operated by the base stations.One of these physical control channels, the so-called physical downlinkcontrol channel (PDCCH) carries control information for scheduling ofdownlink and uplink resources to individual communication devices.Physical downlink control (PDCCH) channels are transmitted on anaggregation of one or several consecutive control channel elements(CCEs). Scheduling is realised by the serving base station transmitting,over the PDCCH, a Downlink Control Information (DCI) to eachcommunication device that has been scheduled resources in the currentscheduling round. Downlink data that has been scheduled this way istransmitted over the so-called Physical Downlink Shared Channel (PDSCH)using the resources allocated by the DCI. The PDSCH resources associatedwith the PDCCH control information (DCI) are normally provided withinthe same subframe, albeit using different frequencies.

The so-called physical uplink control channel (PUCCH) carries, in theuplink from the communication device to the serving base station,information referred to as Uplink Control Information (UCI). The UCIincludes, amongst others, the so-called Hybrid Automatic Repeat Request(HARQ) feedback which is generated by the communication device and sentto the serving base station in response to downlink data transmissionsreceived over the resources specified by the DCI. The UCI may alsoinclude channel quality indication (CQI), although this is optional.Normally, PUCCH resources are allocated to each communication devicesuch that each communication device has time for processing the receiveddownlink data before sending an appropriate (HARQ) Ack/Nack. Typically,PUCCH resources are allocated in the fourth subframe followingtransmission of the corresponding downlink data over the PDSCH, leavinga total of three subframes for processing the received data andgenerating an Ack/Nack.

The more communication devices there are in a cell and the more data iscommunicated for these communication devices, the more controlsignalling and HARQ feedback needs to be transmitted. Therefore, theamount of resources allocated for the PUCCH may change in dependence onthe number of communication devices served by the base station.

In the Rel-13 version of the LTE standards, it is envisioned that thePUCCH will be provided in accordance with the current (Rel-8 based)design. In particular, the current PUCCH design specifies, amongstothers, that:

-   -   the PUCCH is located at an edge of the total available cell        bandwidth and that PUCCH slot hopping can also be applied (slot        hopping is a technique for improving frequency diversity by        frequently alternating the location of the PUCCH physical        resources between opposite edges of the cell bandwidth); and    -   the number of physical resource blocks (PRBs) in a slot that is        available for potential PUCCH transmission is configured by        higher layer signalling using the ‘pusch-HoppingOffset’        parameter.

However, recent developments in telecommunications have seen a largeincrease in the use of machine-type communications (MTC) UEs which arenetworked devices arranged to communicate and perform actions withouthuman assistance. Examples of such devices include smart meters, whichcan be configured to perform measurements and relay these measurementsto other devices via a telecommunication network. Machine-typecommunication devices are also known as machine-to-machine (M2M)communication devices.

MTC devices connect to the network whenever they have data to send to orreceive from a remote ‘machine’ (e.g. a server) or user. MTC devices usecommunication protocols and standards that are optimised for mobiletelephones or similar user equipment. However, MTC devices, oncedeployed, typically operate without requiring human supervision orinteraction, and follow software instructions stored in an internalmemory. MTC devices might also remain stationary and/or inactive for along period of time. The specific network requirements to support MTCdevices have been dealt with in the 3GPP TS 22.368 standard, thecontents of which are incorporated herein by reference.

SUMMARY OF INVENTION Technical Problem

For the Release 13 (Rel-13) version of the standards relating to MTCdevices, support for a reduced bandwidth of 1.4 MHz in downlink anduplink is envisaged. Thus, some MTC devices (referred to as ‘reducedbandwidth MTC devices’) will support only a limited bandwidth (typically1.4 MHz) compared to the total LTE bandwidth and/or they may havefewer/simplified components. This allows such ‘reduced bandwidth’ MTCdevices to be made more economically compared to MTC devices supportinga larger bandwidth and/or having more complicated components.

However, the inventors have realised that, since reduced bandwidth MTCdevices cannot communicate over the entire cell bandwidth, it may notalways be possible to schedule such reduced bandwidth MTC devices inRel-13 using the current (Rel-8 based) PDCCH/PUCCH channel design,especially when PUCCH slot hopping is also employed in the cell.

Further, the lack of network coverage (e.g. when deployed indoors), incombination with the often limited functionality of MTC devices, canresult in such MTC devices having a low data rate and therefore there isa risk of some messages or channels not being received by an MTC device.In order to mitigate this risk, it has been proposed to increase thecoverage of the PDCCH (or enhanced PDCCH (‘EPDCCH’) in Rel-13) tosupport such MTC devices (e.g. corresponding to 20 dB for frequencydivision duplex (FDD) transmissions). To facilitate such enhancedcoverage, each MTC device will need to inform its serving base stationof the amount of coverage required (e.g. 5 dB/10 dB/15 dB/20 dB coverageenhancement) to allow the base station to adjust its control signallingappropriately.

Ideally, physical layer control signalling (such as (E)PDCCH, PUCCH,and/or the like) and higher layer common control information (e.g. SIB,random access response (RAR), paging messages, and/or the like) exhibita high level of commonality between solutions for reduced bandwidthcommunication devices and solutions for coverage enhanced communicationdevices.

However, it is presently not known how to support reduced bandwidth MTCdevices whilst also ensuring that an appropriate coverage enhancementcan be provided when scheduling coverage enhanced MTC devices.

Solution of Problem

The present invention seeks to provide systems, devices and methodswhich at least partially address the above issues.

In an exemplary aspect of the invention, there is provided acommunication apparatus which is operable to communicate with at leastone of a first type mobile station and a second type mobile station, thecommunication apparatus including: a means for assigning a firstfrequency resource for a first uplink control channel of the first typemobile station per slot; and a means for assigning a second frequencyresource for a second uplink control channel of the second type mobilestation per a set of subframe.

In another exemplary aspect of the invention, there is provided a mobilestation which is operable to communicate with a communication apparatus,the mobile station including: a means for determining first frequencyresource which is assigned for a first uplink control channel per a setof subframe; and a means for transmitting the uplink control channelbased on the first frequency resource.

In another exemplary aspect of the invention, there is provided a methodperformed by a communication apparatus which is operable to communicatewith at least one of a first type mobile station and a second typemobile station, the method including: assigning a first frequencyresource for a first uplink control channel of the first type mobilestation per slot; and assigning a second frequency resource for a seconduplink control channel of the second type mobile station per a set ofsubframe.

In another exemplary aspect of the invention, there is provided a methodperformed by a mobile station which is operable to communicate with acommunication apparatus, the method including: determining firstfrequency resource which is assigned for a first uplink control channelper a set of subframe; and transmitting the uplink control channel basedon the first frequency resource.

Aspects of the invention extend to corresponding systems, methods, andcomputer program products such as computer readable storage media havinginstructions stored thereon which are operable to program a programmableprocessor to carry out a method as described in the aspects andpossibilities set out above or recited in the claims and/or to program asuitably adapted computer to provide the apparatus recited in any of theclaims.

Each feature disclosed in this specification (which term includes theclaims) and/or shown in the drawings may be incorporated in theinvention independently (or in combination with) any other disclosedand/or illustrated features. In particular but without limitation thefeatures of any of the claims dependent from a particular independentclaim may be introduced into that independent claim in any combinationor individually.

BRIEF DESCRIPTION OF DRAWINGS

Embodiments of the invention will now be described by way of exampleonly with reference to the attached figures in which:

FIG. 1 schematically illustrates a telecommunication system to whichembodiments of the invention may be applied;

FIG. 2 is a block diagram illustrating the main components of thecommunication device shown in FIG. 1 ;

FIG. 3 is a block diagram illustrating the main components of the basestation shown in FIG. 1 ;

FIG. 4 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 ;

FIG. 5 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 ;

FIG. 6 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 ;

FIG. 7 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 ;

FIG. 8 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 ;

FIG. 9 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 ;

FIG. 10 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 ;and

FIG. 11 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 .

DESCRIPTION OF EMBODIMENTS Overview

FIG. 1 schematically illustrates a mobile (cellular) telecommunicationsystem 1 in which communication devices 3 (such as mobile telephone 3-1and MTC device 3-2) can communicate with each other and/or with othercommunication nodes via an E-UTRAN base station 5 (denoted ‘eNB’) and acore network 7. As those skilled in the art will appreciate, whilst onemobile telephone 3-1, one MTC device 3-2, and one base station 5 areshown in FIG. 1 for illustration purposes, the system, when implemented,will typically include other base stations and communication devices.

The base station 5 is connected to the core network 7 via an S1interface. The core network 7 includes, amongst others: a gateway forconnecting to other networks, such as the Internet and/or to servershosted outside the core network 7; a mobility management entity (MME)for keeping track of the locations of the communication devices 3 (e.g.the mobile telephone and the MTC device) within the communicationnetwork 1; and a home subscriber server (HSS) for storing subscriptionrelated information (e.g. information identifying which communicationdevice 3 is configured as a machine-type communication device) and forstoring control parameters specific for each communication device 3.

The base station 5 is configured to provide a number of controlchannels, including, for example, a physical downlink control channel(PDCCH) and a physical uplink control channel (PUCCH). The PDCCH is usedby the base station 5 for allocating resources to the communicationdevices 3 (typically by sending a UE-specific DCI to each communicationdevice that has been scheduled in the current scheduling round). ThePUCCH is used by the communication devices 3 for sending a UE-specificUCI to the base station (e.g. an appropriate HARQ Ack/Nack correspondingto downlink data received using the resources allocated by the DCI).

Each communication device 3 may fall into one or more of categories ofUEs. A first category of UEs include communication devices that supportonly an earlier release of the LTE standard (e.g. Rel-8, Rel-9, Rel-10,Rel-11, and/or Rel-12). Such group of communication devices are commonlyreferred to as legacy UEs (assuming that the base station 5 is operatingin accordance with Rel-13 of the LTE standards). A second category ofUEs include reduced bandwidth UEs (e.g. Rel-13 MTC devices capable ofusing a 1.4 Mhz bandwidth only), which are not able to communicate overthe entire bandwidth available in the cell of the base station 5. Athird category of UEs includes coverage enhanced UEs (e.g. some MTCdevices), which require certain base station functionalities to besimplified and/or relaxed (although such coverage enhanced UEs maysupport other functionalities as normal).

Beneficially, in order to support reduced bandwidth MTC devices,respective reduced bandwidth MTC specific PUCCH resources are configuredfor each MTC device in such a way that the PUCCH resources used in afirst slot in the time domain (e.g. the first slot of a subframe) andthe PUCCH resources used in a second slot in the time domain (e.g. thesecond slot of the subframe) are limited to being transmitted within thereduced bandwidth (typically 1.4 MHz) supported by the reduced bandwidthMTC device even where slot-to-slot hopping is employed, in which thefrequency position of the PUCCH resources in the second slot effectivelymirrors the frequency position of the PUCCH resources in the first slot,around the centre of the cell bandwidth. A number of specificembodiments are described in which this is achieved.

In one embodiment, for example, this is achieved by ‘over-provisioning’the PUCCH such that the PUCCH resources available for scheduling to MTCdevices include resources that extend from the upper and lowerfrequencies of the cell bandwidth into a central portion of the cellbandwidth that is smaller than the bandwidth of the reduced bandwidthMTC device. For example the central portion may have a bandwidth nogreater than six adjacent resource blocks (˜1.08 MHz) which is less thanthe typical 1.4 MHz bandwidth of a reduced bandwidth MTC device.Beneficially, in this embodiment each category of communication devicescan be allocated PUCCH resources within the same PUCCH and in the samemanner (i.e. with an appropriate slot hopping).

In another embodiment, for example, this is achieved by allocatingresources (a maximum of six adjacent resource blocks) for the MTCdevices to transmit PUCCH control information in a shared channel thatdoes not employ slot hopping. For example, ‘PUCCH’ control informationmay be transmitted using the resources of the physical uplink sharedchannel (PUSCH). Therefore, effectively, the MTC devices may beconfigured to transmit their PUCCH signalling using shared resources(e.g. PUSCH), rather than dedicated resources (e.g. conventional, orlegacy, PUCCH). Beneficially, in this embodiment there is no need to‘over-provision’ the conventional PUCCH to account for the MTC devices(which typically communicate less frequently, and hence they need tosend fewer PUCCH signalling, than other types of communication devices).

In yet another embodiment, for example, this is achieved by providing aseparate, MTC specific, PUCCH channel near a central portion of the cellbandwidth that is smaller than the bandwidth of the reduced bandwidthMTC device (and that is separated from the legacy PUCCH that extendsfrom the edges of the cell bandwidth). For example, such a separate, MTCspecific, PUCCH channel may be provided over the central portion havinga bandwidth no greater than six adjacent resource blocks (˜1.08 MHz).One benefit of this embodiment is that there is no need to share the MTCPUCCH resources with the resources normally used for the uplink sharedchannel communications.

In yet another embodiment, for example, this is achieved by allocating aset of resources forming part of a convention (legacy) PUCCH region toMTC devices and disabling slot hopping in that set of resources. Onebenefit of this embodiment is that PUCCH resources may be provided nearthe edges of the cell bandwidth for each category of communicationdevices.

In yet another embodiment, for example, this is achieved by configuringthe MTC devices to transmit, in a first slot, their PUCCH signallingusing part of the legacy PUCCH resources, at the upper or lower edges ofthe cell bandwidth, that is smaller than the bandwidth of the reducedbandwidth MTC device. In this case, rather than performing conventionalslot hopping in which the PUCCH resources used in the second slot are ata frequency position that mirrors the frequency position of the PUCCHresources in the first slot, the MTC devices are configured to applytime division multiplexing techniques in order to maintain the benefitof frequency diversity otherwise provided by slot hopping. Specifically,after completing its PUCCH transmission in the first slot, but prior totransmitting in the second slot, the MTC device is configured toswitch/re-tune its (reduced bandwidth) transceiver to move itsoperational frequency band to a position that mirrors, around the centreof the cell bandwidth, the position of the operational frequency bandused in the first slot. Once the MTC device has completedswitching/re-tuning its transceiver, it continues its PUCCH transmissionin the second slot at a frequency position (within the entire cellbandwidth) that may (but doesn't have to) mirror, around the centre ofthe cell bandwidth, the frequency position (within the entire cellbandwidth) used in the first slot.

Advantageously, the provision of such MTC specific PUCCH resources inaccordance with any of the above embodiment does not affect theprovision of PUCCH resources for legacy communication devices, becausethere is no need for the base station to change the way its legacy PUCCHis provided.

In summary, the PUCCH is beneficially configured in the cell of the basestation 5 in such a way that different categories of communicationdevices are allocated different types of PUCCH resources. Therefore,legacy communication devices may be allocated resources in aconventional (Rel-8 based) PUCCH, whilst MTC devices may be allocatedresources in the MTC specific PUCCH (in a portion of the cell bandwidththat is smaller than the bandwidth of the reduced bandwidth MTC device).

Therefore, it is possible to support MTC devices (especially reducesbandwidth MTC devices) without sacrificing the backward compatibilityand/or without having to limit the PUCCH bandwidth to 1.4 MHz. Further,it is also possible to support PUCCH slot hopping for compatiblecommunication devices and thereby benefit from frequency diversity.

Beneficially, in order to provide the required commonality betweensolutions for reduced bandwidth MTC devices and the solutions forcoverage enhanced MTC devices, in each of the embodiments summarisedabove, the reduced bandwidth MTC PUCCH techniques can also be appliedfor coverage enhanced MTC devices. Unlike the reduced bandwidth MTCdevice, however, in the case of coverage enhanced MTC devices everyrelevant channel (e.g. comprising the PDSCH, PUCCH and the PRACH as wellas the EPDCCH) is repeated in multiple subframes where the number ofrepetitions depends on the level of coverage enhancement.

<Communication Device>

FIG. 2 is a block diagram illustrating the main components of thecommunication device 3 shown in FIG. 1 . The communication device 3 maybe an MTC device or a mobile (or ‘cellular’) telephone configured as amachine-type communication device. The communication device 3 comprisesa transceiver circuit 31 which is operable to transmit signals to, andto receive signals from, the base station 5 via at least one antenna 33.Typically, the communication device 3 also includes a user interface 35which allows a user to interact with the communication device 3, howeverthis user interface 35 may be omitted for some MTC devices.

The operation of the transceiver circuit 31 is controlled by acontroller 37 in accordance with software stored in memory 39. Thesoftware includes, among other things, an operating system 41, acommunication control module 43, and an MTC module 45.

The communication control module 43 controls communications between thecommunication device 3 and the base station 5 and/or other communicationnodes (via the base station 5). As shown in FIG. 2 , the communicationcontrol module 43 includes, amongst others, an EPDCCH module portion(for managing communications over the enhanced physical downlink controlchannel), a PDSCH module portion (for managing communications over thephysical downlink shared channel), and a PUCCH module portion (formanaging communications over the physical uplink control channel).

The MTC module 45 is operable to carry out machine-type communicationtasks. For example, the MTC module 45 may (e.g. periodically) receivedata from a remote server (via the transceiver circuit 31) overresources allocated to the MTC device 3 by the base station 5. The MTCmodule 45 may also collect data for sending (e.g. periodically and/orupon detecting a trigger) to a remote server (via the transceivercircuit 31).

<Base Station>

FIG. 3 is a block diagram illustrating the main components of the basestation 5 shown in FIG. 1 . The base station 5 comprises an E-UTRAN basestation (eNB) comprising a transceiver circuit 51 which is operable totransmit signals to, and to receive signals from, the communicationdevices 3 via one or more antennas 53. The base station 5 is alsooperable to transmit signals to and to receive signals from a corenetwork 7 via an appropriate core network interface 55 (such as an S1interface). The operation of the transceiver circuit 51 is controlled bya controller 57 in accordance with software stored in memory 59.

The software includes, among other things, an operating system 61, acommunication control module 63, and a UE category determination module65.

The communication control module 53 controls communications with thecommunication devices 3 (including any MTC devices). The communicationcontrol module 53 is also responsible for scheduling the resources to beused by the communication devices 3 served by this base station 5. Asshown in FIG. 3 , the communication control module 63 includes, amongstothers, an EPDCCH module portion (for managing communications over theenhanced physical downlink control channel), a PDSCH module portion (formanaging communications over the physical downlink shared channel), anda PUCCH module portion (for managing communications over the physicaluplink control channel).

The UE category determination module 65 determines the category of thecommunication devices 3 served by the base station 5, based on, forexample, information obtained from the communication devices 3 and/orfrom another network node (e.g. the HSS). When appropriate, the UEcategory determination module 65 provides information identifying thecategory of each served communication devices to the other modules, e.g.the communication control module 53, so that the other modules canadjust their operation accordingly.

In the above description, the communication device 3 and the basestation 5 are described for ease of understanding as having a number ofdiscrete modules. Whilst these modules may be provided in this way forcertain applications, for example where an existing system has beenmodified to implement the invention, in other applications, for examplein systems designed with the inventive features in mind from the outset,these modules may be built into the overall operating system or code andso these modules may not be discernible as discrete entities.

The following is a description of various ways in which the physicaluplink control channel may be provided in LTE systems.

<PUCCH Design in Rel-8>

FIG. 4 illustrates an exemplary way in which PUCCH mapping to PRBs andPUCCH slot hopping may be performed in accordance with the PUCCH designfor Rel-8 of LTE. It will be appreciated that this PUCCH design (whichis also referred to as ‘legacy PUCCH’) is not limited to Rel-8 LTEsystems and it is also used in later versions of the LTE standards (e.g.Rel-9 to Rel-12) for backward compatibility with user equipmentsupporting only the Rel-8 version of LTE.

The bandwidth of the cell comprises a number (‘N_RB’) of physicalresource blocks (i.e. cell resource blocks #0 through #N_RB shown inFIG. 4 , where ‘N_RB’ denotes the total number of physical resourceblocks per slot). As explained above, the PUCCH is typically located at(or near) the edges of the available cell bandwidth. The number ofphysical resource blocks in a slot for potential PUCCH transmission isconfigured by higher layer signalling using the ‘pusch-HoppingOffset’parameter (denoted ‘N_HO_RB’ in FIG. 4 ). It will be appreciated thatthe value of the ‘pusch-HoppingOffset’ parameter depends on the numberof communication devices served by the base station in its cell. In theexample shown in FIG. 4 , N_HO_RB=12, i.e. the PUCCH in this exampleincludes a total of twelve resource blocks (six at each edge of eachslot). Therefore, a total of twelve resource blocks are allocated forthe PUCCH (although not all of these resource blocks are necessarilyused in every slot, since in each subframe the actual number of resourceblocks used depends on the number of communication devices scheduled inthat particular subframe). The ‘pusch-HoppingOffset’ parameter may besignalled to the UEs using RRC configuration signalling.

It will be appreciated that such a legacy PUCCH area may be providednear an edge of the slots such that it does not exceed the 1.4 MHzbandwidth limit supported by some of the MTC devices. For example, inthe scenario shown in FIG. 4 , the six neighbouring resource blocks neareither edge of the cell bandwidth correspond to such a 1.4 MHz bandwidth(or less). Therefore, a limited bandwidth MTC device would be able totransmit signals over either the top ‘legacy PUCCH’ area or the bottom‘legacy PUCCH’ area (but not both areas) and even if the value ofN_HO_RB does exceed ‘6’, the MTC device will only transmit maximum 6 RBsthat contains it PUCCH part in any given subframe.

However, in accordance with Rel-8 PUCCH design, PUCCH slot hopping isalso applied in order to improve frequency diversity in the cell.Therefore, as indicated in FIG. 4 by a diagonal arrow for PUCCH resourceblock #1, the location of each PUCCH resource block is alternatingbetween the two opposite edges of the cell bandwidth between two slots(i.e. PUCCH resource block #1 is provided via cell resource block #N_RBin slot 1 and via cell resource block #0 in slot 2).

Consequently, a reduced bandwidth MTC device (such as the MTC device 3-2of FIG. 1 ) having a typical bandwidth of 1.4 MHz may not be able tocommunicate (e.g. transmit signals) at both ends of the cell bandwidthin a particular subframe. Therefore, in case of the scenario shown inFIG. 4 , such an MTC device transmits its scheduled PUCCH controlinformation at both resource blocks #0 (in slot 1) and #N_RB (in slot2)—although the MTC device may be able to switch from one 1.4 MHzportion to a different 1.4 MHz portion of the cell bandwidth from onesubframe to another.

This issue may be overcome by employing one or more of the followingPUCCH design options A to G (described with reference to FIGS. 5 to 10below), whilst also maintaining backward compatibility withcommunication devices supporting the legacy (Rel-8 based) PUCCH.

It will be appreciated that these options are not mutually exclusive andany of the options A to G may be combined within the same system, eitherwithin a single cell and/or in neighbouring cells. For example, the basestation 5 may be configured to change from one PUCCH configuration toanother, e.g. periodically, in dependence on the number of MTC devices 2in its cell, in dependence on the overall load in the cell, and/or thelike.

<Operation—Option A>

FIG. 5 illustrates an exemplary way in which an MTC specific physicaluplink control channel can be provided in the system shown in FIG. 1 .

This embodiment is based on the concept of over-provisioning the PUCCH.Such over-provisioning can be realised by the base station 5 selecting(using its PUCCH module portion) the value of the ‘push-HoppingOffset’parameter (denoted ‘N_HO_RB’ in FIG. 5 ) such that it is large enough toinclude (at least some of) the physical resource blocks located near thecentre six cell resource blocks. Advantageously, in this case an MTCspecific PUCCH area may be provided over (some of) the centre sixphysical resource blocks from among the cell resource blocks #0 to #N_RB(i.e. over a bandwidth not exceeding 1.4 MHz). Therefore, even if PUCCHslot hopping is enabled in the cell, the PUCCH resources allocated toMTC device alternate between physical resource blocks that are locatedwithin a 1.4 MHz bandwidth.

Advantageously, the provision of an MTC specific PUCCH area in thismanner does not affect the provision of a legacy (Rel-8 based) PUCCHsince the range of physical resource blocks used for the PUCCH aredefined, starting from the edges of each slot, by the ‘N_HO_RB’parameter. Therefore, a sufficient level of frequency diversity may bemaintained for compatible communication devices by allocating resourceblocks from within such an over-provisioned PUCCH area but closer to theedges of the slots (e.g. outside the centre six physical resourceblocks).

It will be appreciated that the base station 5 may be configured toobtain (using its UE category determination module 65) informationidentifying whether a particular communication device (e.g. the MTCdevice 3-2) comprises a machine-type communication device and/orfunctionality. The base station 5 may obtain such information, forexample, from the HSS and/or from the communication device itself. Thebase station 5 may also be configured to obtain information identifyingwhether a particular MTC device comprises a reduced bandwidth MTC deviceor a coverage enhanced MTC device. Therefore, based on the obtainedinformation, the base station 5 can allocate (using its PUCCH moduleportion) appropriate PUCCH resources: i) to MTC devices (at leastreduced bandwidth MTC devices or, optionally, to all MTC devices) in theMTC specific PUCCH area comprising the centre six physical resourceblocks; and to other communication devices (e.g. regular mobiletelephones and/or coverage enhanced MTC devices) outside the centre sixphysical resource blocks (preferably near the edges of the slots iffrequency diversity is required).

It will be appreciated that since Rel-13 MTC devices are expected tosupport applications with very small data rates (i.e. small pay loads),there is no need for such MTC devices to support the so-called MultipleInput Multiple Output (MIMO) technique (and/or to have multipleantennas). This may in turn reduce the processing complexity and powerconsumption of such MTC devices. Further, for Rel-13 MTC devices it issufficient for the base station 5 to transmit a single transport blockin the downlink which will only require a single Ack/Nack (in a singleUCI) to be conveyed in the uplink PUCCH channel, further reducing thecomplexity of the required MTC specific PUCCH.

In addition, there is also no need to obtain CQI feedback from the MTCdevices because of their narrow (1.4 MHz) supported bandwidth.Therefore, it will be appreciated that only PUCCH Format 1 and 1a wouldbe needed for MTC devices in Rel-13 (i.e. PUCCH Formats 1b/2/2a/2b/3 maynot be needed).

<Operation—Option B>

FIG. 6 illustrates another exemplary way in which an MTC specificphysical uplink control channel can be provided in the system shown inFIG. 1 .

This embodiment is based on the concept of carrying the PUCCH controlsignalling (for MTC devices) over the PUSCH channel. Specifically, thePUSCH in this example is provided near the centre portion of thephysical resource blocks used in the cell of the base station 5 (e.g.near the centre six (or fewer) cell resource blocks). However, ratherthan carrying only shared uplink signalling, the PUSCH in thisembodiment is adapted to carry the PUCCH control signalling for MTCdevices. Therefore, in this example, there is no need forover-provisioning the PUCCH (i.e. a legacy PUCCH, preferably with slothopping enabled, can be provided for non-MTC communication deviceswithout the base station 5 having to select a large ‘N_HO_RB’ value).

Beneficially, even if PUCCH slot hopping is enabled in the cell forlegacy (non-MTC) communication devices, the PUCCH resources allocated toMTC device remain unaffected and/or can alternate between physicalresource blocks of the PUSCH that are located within a 1.4 MHz bandwidth(around the centre of the cell bandwidth).

In practice, this option means that either the control information (e.g.UCI) sent by the MTC devices needs to be multiplexed with the datanormally transmitted over the PUSCH or the PUSCH resource blocksallocated to MTC devices only carry the control information (UCI). Itwill be appreciated that it is possible to send information on the PUSCHwithout any scheduled uplink data (UL-SCH), for example, as specified insection 5.2.4 of 3GPP TS 36.212, and in sections 8.6.1 and 8.6.2 of TS36.213, the contents of which are incorporated herein by reference. Thistechnique may be extended to enable MTC devices to send the controlinformation (e.g. UCI) without multiplexing it with other PUSCH data.

If the control information sent by a particular MTC device is beingmultiplexed with PUSCH data, then the base station 5 may be configuredto allocate (using its communication control module 63) the uplinkphysical resource block for a given MTC device using the uplink grantcontrol data that schedules the PUSCH data (that is to be multiplexedwith that MTC device's control information).

If the control information by a particular MTC device is transmitted onthe PUSCH without scheduling any PUSCH data (i.e. without multiplexing),then the number of the uplink physical resource blocks for a given MTCdevice that will carry the associated control information can be givenin a number of ways, for example, including:

-   -   indicated dynamically by the uplink grant mechanism (e.g. using        an appropriate DCI format) that is normally used for scheduling        PUSCH data;    -   configured by RRC signalling (e.g. semi-statically); and/or    -   based on a semi-persistent scheduling (SPS) allocation (i.e. the        physical resource block to be used by a given MTC device may be        configured for the MTC device by an appropriate SPS        configuration).

<Operation—Option C>

FIG. 7 illustrates another exemplary way in which an MTC specificphysical uplink control channel can be provided in the system shown inFIG. 1 .

In this example, the base station 5 provides an MTC specific PUCCH. Itwill be appreciated that, for backward compatibility, such an MTCspecific PUCCH may be provided in addition to a regular, legacy PUCCH(defined by ‘N_HO_RB’) provided at the edges of the slots.

As shown in FIG. 7 , the MTC specific PUCCH is provided over a maximumof six physical resource blocks (i.e. over a bandwidth not exceeding 1.4MHz) near the centre of the range of physical resource blocks #0 to#N_RB of the cell. The MTC specific PUCCH area includes MTC resources #0to 5, which may be used by a maximum of six MTC devices per schedulinground. However, since the MTC devices are typically transmitting smallbursts of data, each MTC resource #0 to 5 may be re-allocated to adifferent MTC device in a subsequent scheduling round.

It will be appreciated that, if appropriate, such an MTC specific PUCCHmay be provided solely for the use of MTC devices (e.g. Rel-13 reducedbandwidth MTC devices) even without slot hopping enabled (i.e. withoutbackward compatibility). In this case, it will be appreciated that eachMTC device may be scheduled to transmit, in both slots, using the samesix resource blocks that contain the PUCCH information for that MTCdevice.

If appropriate (e.g. when slot hopping is not used), it will also beappreciated that the MTC specific PUCCH may also be provided closer to(or even adjacent to) the legacy PUCCH rather than at the centre area(as shown in FIG. 7 ).

<Operation—Option D>

FIG. 8 illustrates yet another exemplary way in which an MTC specificphysical uplink control channel can be provided in the system shown inFIG. 1 .

Effectively, option D can be seen as a modification of option C.However, in this case the MTC specific PUCCH is provided as part of thelegacy PUCCH rather than adjacent to it.

Therefore, when the base station 5 configures (using its PUCCH moduleportion) the value of the ‘push-Hoppingoffset’ parameter (denoted‘N_HO_RB’ in FIG. 8 ), the base station selects the value such that italso includes (a maximum of) six physical resource blocks locatedimmediately after the legacy PUCCH area (provided at the edges) towardsthe centre of the slots. In the example shown in FIG. 8 there arethree-three MTC specific PUCCH resource blocks allocated next to bothportions of the legacy PUCCH provided at the lower and upper edges ofthe slots (although it is possible to provide up to six MTC specificPUCCH resource blocks next to each portion of the legacy PUCCH, i.e. notexceeding 1.4 MHz).

It will be appreciated that whilst in the legacy PUCCH area slot hoppingmay be supported (for frequency diversity), the MTC specific PUCCH isprovided without slot hopping enabled in order to ensure compatibilitywith Rel-13 reduced bandwidth MTC devices (and/or similar). Therefore,regardless whether or not PUCCH slot hopping is enabled in the cell forlegacy devices, the PUCCH resources allocated to MTC devices remainwithin the same resource block (and/or alternate only within the same1.4 MHz bandwidth) in both slots.

<Operation—Option E>

FIG. 9 illustrates yet another exemplary way in which an MTC specificphysical uplink control channel can be provided in the system shown inFIG. 1 .

In this example, only a legacy PUCCH is configured by the‘push-HoppingOffset’ parameter (denoted ‘N_HO_RB’ in FIG. 9 ). However,in this case the MTC device is configured to transmit over its allocatedPUCCH resource block in a time division multiplexing (TDM) manner. Inother words, as illustrated in FIG. 9 , the base station 5 allocates(using its PUCCH module portion) a PUCCH resource (e.g. PUCCH resourceblock #1 forming part of a legacy PUCCH) to the MTC device (denoted ‘UE’in FIG. 9 ). However, rather than performing slot hopping between slot 1and slot 2 (which would require a transceiver that is capable ofsimultaneously operating over the entire cell bandwidth), the MTC devicetransmits only a first part of its scheduled uplink data for theduration of slot 1. Then, after slot 1, the MTC device performs anappropriate switching and/or tuning if its transmitter (Tx) 31 to afrequency band covering the physical resource block in slot 2corresponding to the PUCCH resource block #1 after slot hopping. AfterTx switching/tuning, the MTC device transmits the remaining part of itsscheduled uplink data for the duration of slot 2.

It means that a reduced bandwidth MTC device (e.g. a Rel-13 MTC device)may be scheduled to transmit (using its transceiver circuit 31) over amaximum of six neighbouring resource blocks in the first slot (thatcontains the MTC device's corresponding PUCCH information) and thenswitch/tune its transceiver circuit 31 to the corresponding resourceblock(s) of the second slot.

As a modification of this embodiment, each physical resource block maybe shared between two MTC devices. In other words, the base station 5may allocate a PUCCH resource (e.g. PUCCH resource block #1) to a firstMTC device for the duration of slot 1, and allocate the same PUCCHresource to a second MTC device for the duration of slot 2. In thiscase, there is no need for either MTC device to perform any Txswitching/tuning between slots 1 and 2 (although the MTC devices mayneed to suspend transmission for the duration of the slot in which thephysical resource block is allocated to a different MTC device).However, since MTC devices normally transmit a relatively low amount ofdata, this modification may not have any significant drawback (and mayeven improve the MTC device's overall power consumption).

<Operation—Option F>

In accordance with the LTE FDD specifications for Rel-8, a communicationdevice 3 needs to time its Ack/Nack transmissions (confirmingsuccessful/unsuccessful receipt of a downlink packet) as follows:

-   -   i) in subframe n−4, the communication device 3 receives (E)PDCCH        control signalling (which indicates that downlink resources have        been allocated to the communication device 3 for receiving        downlink data) and detects associated PDSCH signalling (i.e.        downlink data for the communication device 3);    -   ii) in subframe n−4, the communication device 3 receives the        scheduled downlink data from the base station 5 via the PDSCH;    -   iii) in subframes n−3 to n−1, the communication device 3        processes the received downlink data; and    -   iv) in subframe n, the communication device 3 transmits to the        base station 5: an acknowledgement (HARQ-ACK) upon successful        receipt of the PDSCH control signalling; or a negative        acknowledgement (HARQ-NACK) upon unsuccessful receipt of the        PDSCH control signalling.

In accordance with this timing method, the communication device 3receives both the (E)PDCCH and the PDSCH in the same subframe (i.e. insubframe n−4) and the communication device 3 has a maximum of threesubframes (i.e. from subframe n−3 to subframe n−1) to process the PDSCHcontrol signalling before sending an appropriate HARQ Ack/Nack responseto the base station 5.

However, in LTE Rel-13, MTC devices are not expected to be able toreceive their EPDCCH and PDSCH signalling within the same subframe. Thisis because the EPDCCH and the PDSCH are not necessarily transmittedwithin the same 1.4 MHz bandwidth that the (reduced bandwidth) MTCdevices are capable of using in that subframe. Therefore, in LTE Rel-13the following options are envisaged for the timing the Ack/Nacktransmissions by MTC devices for their PDSCH signalling:

1) No EPDCCH Control Signalling is Transmitted in Subframe n−4:

In this case the MTC device detects its PDSCH control signalling insubframe n−4; and transmits a corresponding (HARQ) ACK/NACK in subframen. Therefore, in this case the EPDCCH and the PDSCH signalling for theMTC device are not transmitted in the same subframe (as they would be inaccordance with legacy, e.g. Rel-8 practices).

It will be appreciated therefore that uplink (PUCCH) resources fortransmitting the Ack/Nack may be allocated to the MTC devicessemi-statically (e.g. using higher layer signalling similar to the(Rel-8) SPS PUCCH resource allocation technique, which is illustrated inTable 9.2-2 of 3GPP TS 36.213). Alternatively, the EPDCCH controlsignalling may be transmitted in subframe n−5.

2) No PDSCH Control Signalling Transmitted in Subframe n−4:

In this case (which is illustrated in FIG. 10 ) the MTC device detectsits EPDCCH control signalling in subframe n−4; detects its PDSCH controlsignalling in subframe n−3; and transmits a corresponding (HARQ)ACK/NACK in subframe n. Beneficially, the base station 5 is notrestricted in this case to transmit both the EPDCCH and the PDSCH overthe same 1.4 MHz bandwidth that (reduced bandwidth) MTC devices arecapable of using in a given subframe (although the MTC devices may needto switch from the EPDCCH frequency band to the PDSCH frequency band, ifdifferent, between subframes n−4 and n−3).

In this case therefore the time duration available for the MTC device toprocess the received PDSCH signalling is reduced to approximately twosubframes (from three subframes in accordance with the above Rel-8Ack/Nack transmission method). However, since a typical MTC device isnot receiving large blocks of data, such a shortened processing time isexpected to be sufficient.

<Operation—Option G>

Since in Rel-13 there expected to be a high level of commonality betweenthe solutions for bandwidth reduced communication devices and coverageenhanced communication devices, it will be appreciated that the abovedescribed options may be applied for coverage enhanced MTC devices aswell.

However, as illustrated in FIG. 11 , in this case each relevant channel(for example, the EPDCCH, the PDSCH, the PUCCH, and/or the PRACH) isrepeated in multiple subframes (i.e. in the time domain) and theinformation transmitted in each channel is combined by the MTC device inorder to increase detectability of that channel.

FIG. 11 illustrates a modification of the embodiment shown in FIG. 10(i.e. option F/2) in order to support (coverage enhanced) MTC deviceswhen repetition of the relevant channels is enabled.

Specifically, in this case both the EPDCCH and the PDSCH are repeated bythe base station 5. Similarly, the MTC device is configured to transmitan Ack/Nack for each repetition of the PDSCH signalling. However, thereare only three subframes allocated for processing the received(repeated) PDSCH signalling and the MTC device is configured to send thecorresponding Ack/Nack transmissions in successive subframes (i.e.without any additional subframes allocated for processing between twosubsequent acknowledgements).

Therefore, as illustrated in FIG. 11 for a coverage enhancementrequiring three repetitions (i.e. a total of four transmissions of thesame information), the base station 5 transmits the same EPDCCHsignalling in each of subframes n−4 to n−1 (a total of four subframes).Next, the base station 5 transmits the (same) PDSCH signalling in eachof subframes n to n+3 (a total of four subframes). Subframes n+4 to n+6(i.e. a total of three subframes) are allocated for the MTC device 3 forprocessing the received PDSCH signalling (i.e. to determine whether ornot the downlink data was received successfully). Finally, in subframesn+7 to n+10 (a total of four subframes), the MTC device transmits theappropriate Ack/Nack to the base station in dependence on the result ofthe processing.

It will be appreciated that in this case the PUCCH resources (fortransmitting the Ack/Nack) may be allocated to the MTC devicesemi-statically (e.g. using higher layer signalling similar to the(Rel-8) SPS PUCCH resource allocation technique shown in Table 9.2-2 of3GPP TS 36.213).

Modifications and Alternatives

Detailed embodiments have been described above. As those skilled in theart will appreciate, a number of modifications and alternatives can bemade to the above embodiments whilst still benefiting from theinventions embodied therein.

In some of the above embodiments, information relating to the PUCCHallocations may be signalled to the MTC device via higher layers (e.g.by configuring semi-persistent scheduling for the MTC device).Alternatively or additionally, some or all of this information can beobtained by the MTC device in a different manner. Furthermore, theapplicable PUCCH configuration may not be explicitly signalled by thebase station and may instead be determined based upon other information,such as a cell ID associated with the base station and/or a device IDassociated with the MTC device. This has the benefit of reducing theamount of data that has to be signalled to the communication devices.

It will be appreciated that although the communication system isdescribed in terms of the base station operating as a E-UTRAN basestation (eNB), the same principles may be applied to base stationsoperating as macro or pico base stations, femto base stations, relaynodes providing elements of base station functionality, home basestations (HeNB), or other such communication nodes.

In the above embodiments, an LTE telecommunications system wasdescribed. As those skilled in the art will appreciate, the techniquesdescribed in the present application can be employed in othercommunications systems, including earlier 3GPP type systems. Othercommunications nodes or devices may include user devices such as, forexample, personal digital assistants, laptop computers, web browsers,etc.

In the embodiments described above, the base station and thecommunication device each include transceiver circuitry. Typically, thiscircuitry will be formed by dedicated hardware circuits. However, insome embodiments, part of the transceiver circuitry may be implementedas software run by the corresponding controller.

In the above embodiments, a number of software modules were described.As those skilled in the art will appreciate, the software modules may beprovided in compiled or un-compiled form and may be supplied to the basestation or the user device as a signal over a computer network, or on arecording medium. Further, the functionality performed by part or all ofthis software may be performed using one or more dedicated hardwarecircuits.

In the above embodiments, machine-type communication devices and mobiletelephones are described. However, it will be appreciated that mobiletelephones (and similar user equipment) may also be configured tooperate as machine-type communication devices. For example, the mobiletelephone 3-1 may include (and/or provide the functionality of) the MTCmodule 45.

Examples of MTC Applications

It will be appreciated that each communication device may support one ormore MTC applications. Some examples of MTC applications are listed inthe following table (source: 3GPP TS 22.368, Annex B). This list is notexhaustive and is intended to be indicative of the scope of machine-typecommunication applications.

TABLE 1 Service Area MTC applications Security Surveillance systemsBackup for landline Control of physical access (e.g. to buildings)Car/driver security Tracking & Tracing Fleet Management Order ManagementPay as you drive Asset Tracking Navigation Traffic information Roadtolling Road traffic optimisation/steering Payment Point of salesVending machines Gaming machines Health Monitoring vital signsSupporting the aged or handicapped Web Access Telemedicine points Remotediagnostics Remote Maintenance/Control Sensors Lighting Pumps ValvesElevator control Vending machine control Vehicle diagnostics MeteringPower Gas Water Heating Grid control Industrial metering ConsumerDevices Digital photo frame Digital camera eBook

Various other modifications will be apparent to those skilled in the artand will not be described in further detail here.

This invention has been described by way of embodiments above, but thisinvention is not limited to the embodiments. A part or the entirety ofthe above-mentioned embodiments may be described by way of the followingsupplementary notes, but this invention is not limited to the followingsupplementary notes.

(Supplementary Note 1)

A communication node for a communication system, wherein thecommunication node comprises:

-   -   means for operating a cell having a cell bandwidth;    -   means for communicating, with a plurality of different types of        communication devices within said cell, wherein said plurality        of different types of communication devices include a reduced        bandwidth machine-type communication, ‘MTC’, device having a        bandwidth that is small compared to the cell bandwidth; and    -   means for allocating frequency resources respectively to each        communication device operating within said cell, for use in        transmitting uplink control data, in dependence on whether or        not that communication device is an MTC device;    -   wherein said allocating means is operable to allocate said        frequency resources such that: when the communication device is        a reduced bandwidth MTC device, said MTC device communicates        uplink control data using a first frequency resource in a first        slot of a subframe and a second frequency resource in a second        slot of that subframe wherein said first frequency resource and        said second frequency resource share the same frequency or are        separated in frequency by no more than the bandwidth of the        reduced bandwidth MTC device; and when the communication device        is not a reduced bandwidth MTC device, said communication device        that is not a reduced bandwidth MTC device communicates uplink        control data using a first non-MTC frequency resource in the        first slot of a subframe and a second non-MTC frequency resource        in the second slot of that subframe wherein said first non-MTC        frequency resource and said second non-MTC frequency resource        are separated in frequency by more than the bandwidth of the        reduced bandwidth MTC device; and    -   wherein said communicating means is operable to receive uplink        control information from each communication device operating        within said cell using the respective frequency resources        allocated to each communication device operating within said        cell in dependence on whether or not that communication device        is an MTC device.

(Supplementary Note 2)

A communication node of the supplementary note 1 wherein said firstfrequency resource and said second frequency resource are separated infrequency by no more than the bandwidth of the reduced bandwidth MTCdevice and are respectively above and below a centre frequency of saidcell bandwidth.

(Supplementary Note 3)

A communication node of the supplementary note 1 wherein said firstfrequency resource and said second frequency resource share the samefrequency.

(Supplementary Note 4)

A communication node of any one of the supplementary notes 1 of 3wherein said first frequency resource, said second frequency resource,said first non-MTC resource and said second non-MTC resource all formpart of a common uplink control channel region (e.g. a physical uplinkcontrol channel, ‘PUCCH’).

(Supplementary Note 5)

A communication node of any one of the supplementary notes 1 of 3wherein said first non-MTC resource and said second non-MTC resourceform part of an uplink control channel region (e.g. a physical uplinkcontrol channel, TUCCH′) that does not extend across a centre of thecell bandwidth, and said first frequency resource and said secondfrequency resource form part of another separate region.

(Supplementary Note 6)

A communication node of the supplementary note 5 wherein said separateregion extends across the centre of the cell bandwidth.

(Supplementary Note 7)

A communication node of the supplementary note 5 or 6 wherein said firstfrequency resource and said second frequency resource form part of afurther MTC dedicated uplink control channel region (e.g. an MTCphysical uplink control channel, TUCCH′) that is separate from saiduplink control channel region comprising said first non-MTC resource andsaid second non-MTC resource.

(Supplementary Note 8)

A communication node of the supplementary note 5 or 6 wherein said firstfrequency resource and said second frequency resource form part of anuplink shared channel region (e.g. a shared data channel/physical uplinkshared channel, ‘PUSCH’).

(Supplementary Note 9)

A communication node of any one of the supplementary notes 1 to 8wherein said communicating means is further operable to communicate,with an enhanced coverage MTC device having enhanced coverage comparedto other MTC devices and wherein said allocating means is operable toallocate said frequency resources such that: when the communicationdevice is an enhanced coverage MTC device, said MTC device communicatesuplink control data using a further first frequency resource in a firstslot of a subframe and a further second frequency resource in a secondslot of that subframe wherein said further first frequency resource andsaid further second frequency resource share the same frequency or areseparated in frequency by no more than the bandwidth of a reducedbandwidth MTC device.

(Supplementary Note 10)

A machine-type communication, ‘MTC’, device for a communication systemin which a plurality of different types of communication devices cancommunicate with a communication node that operates a cell having a cellbandwidth, wherein the plurality of different types of communicationdevices include a reduced bandwidth machine-type communication, ‘MTC’,device having a bandwidth that is small compared to the cell bandwidth,wherein the MTC device comprises:

-   -   means for communicating with the communication node within the        cell operated by that communication node; and    -   means for obtaining an allocation of frequency resources, for        use in transmitting uplink control data to the communication        node, wherein said allocation is such that said communicating        means communicates uplink control data using a first frequency        resource in a first slot of a subframe and a second frequency        resource in a second slot of that subframe wherein said first        frequency resource and said second frequency resource share the        same frequency or are separated in frequency by no more than the        bandwidth of a reduced bandwidth MTC device; and wherein said        communicating means is operable to transmit uplink control        information using the allocation of frequency resources.

(Supplementary Note 11)

A machine-type communication, ‘MTC’, device for a communication systemin which a plurality of different types of communication devices cancommunicate with a communication node that operates a cell having a cellbandwidth, wherein the plurality of different types of communicationdevices include a reduced bandwidth machine-type communication, ‘MTC’,device having a bandwidth that is small compared to the cell bandwidth,wherein the MTC device comprises:

-   -   means for communicating with the communication node within the        cell operated by that communication node and using frequency        resources within a frequency of an MTC frequency band;    -   means for moving a carrier frequency of said MTC frequency band;        and    -   means for obtaining an allocation of frequency resources, for        use in transmitting uplink control data to the communication        node wherein said allocation is such that said communicating        means communicates uplink control data using a first frequency        resource in a first slot of a subframe and a second frequency        resource in a second slot of that subframe wherein said first        frequency resource and said second frequency resource share the        same frequency or are separated in frequency by more than the        bandwidth of a reduced bandwidth MTC device;    -   wherein said carrier frequency moving means is operable to move        said carrier frequency between said first slot and said second        slot such that said MTC frequency band includes the first        frequency resource in the first slot of the subframe and        includes the second frequency resource in the second slot of        said subframe; and    -   whereby said communicating means is operable to transmit uplink        control information using the first frequency resource in the        first slot of the subframe and to transmit uplink control        information using the second frequency resource in the second        slot of said subframe.

(Supplementary Note 12)

An MTC device of the supplementary note 10 or 11 wherein said MTC deviceis an enhanced coverage MTC device.

(Supplementary Note 13)

An MTC device of the supplementary note 10 or 11 wherein said MTC deviceis a reduced bandwidth MTC device.

(Supplementary Note 14)

A communication node for a communication system, wherein thecommunication node comprises:

-   -   means for operating a cell; and    -   means for communicating with a plurality of different types of        communication devices within said cell using radio frames, each        radio frame comprising a sequence of subframes, wherein said        plurality of different types of communication devices include a        machine-type communication, ‘MTC’, device;    -   wherein said communicating means is operable:    -   to provide downlink control channel signalling for at least one        MTC device in a first of said subframes, and to repeat said        downlink control channel signalling in at least one subsequent        subframe;    -   to provide downlink shared channel signalling for said at least        one MTC device in a subframe subsequent to said subframes in        which said downlink control channel signalling is provided and    -   to repeat said downlink shared channel signalling in at least        one subsequent subframe; and    -   to receive, from the at least one MTC device, uplink control        information relating to said downlink shared channel signalling        in a subframe subsequent to said subframes in which said        downlink shared channel signalling is provided and to receive a        repetition of said uplink control information in at least one        subsequent subframe.

(Supplementary Note 15)

A communication node of the supplementary note 14 further comprisingmeans for semi-statically allocating resources to said at least one MTCdevice for use in transmitting said uplink control information relatingto said downlink shared channel signalling.

(Supplementary Note 16)

A communication node of the supplementary note 14 or 15 wherein saidcommunicating means is operable to: first receive, from the at least oneMTC device, said uplink control information relating to said downlinkshared channel signalling in a subframe that is a fourth subframesubsequent to a last of said subframes in which said downlink sharedchannel signalling is provided.

(Supplementary Note 17)

A machine-type communication, ‘MTC’, device for a communication system,wherein the MTC device comprises:

-   -   means for communicating, with a communication node within a cell        operated by that communication node, using radio frames, each        radio frame comprising a sequence of subframes;    -   wherein said communicating means is operable:    -   to receive downlink control channel signalling for said MTC        device in a first of said subframes, and a repetition of said        downlink control channel signalling in at least one subsequent        subframe;    -   to receive downlink shared channel signalling for said MTC        device in a subframe subsequent to said subframes in which said        downlink control channel signalling is received and a repetition        of said downlink shared channel signalling in at least one        subsequent subframe; and    -   to provide, to said communication node, uplink control        information relating to said downlink shared channel signalling        in a subframe subsequent to said subframes in which said        downlink shared channel signalling is received and to repeat        said uplink control information in at least one subsequent        subframe.

(Supplementary Note 18)

A communication node for a communication system, wherein thecommunication node comprises:

-   -   means for operating a cell;    -   means for communicating with a plurality of different types of        communication devices within said cell using radio frames, each        radio frame comprising a sequence of subframes, wherein said        plurality of different types of communication devices include a        machine-type communication, ‘MTC’, device; and    -   means for semi-statically allocating resources to at least one        MTC device for use in transmitting uplink control information        relating to downlink shared channel signalling;    -   wherein said communicating means is operable:    -   to provide downlink shared channel signalling for said at least        one MTC device in a subframe; and    -   to receive from the at least one MTC device, using said        semi-statically allocated resources, uplink control information        relating to said downlink shared channel signalling in a        subframe subsequent to said subframe in which said downlink        shared channel signalling is provided, wherein the subframe in        which said uplink control information is received is a fourth of        a plurality of subframes subsequent to said subframe in which        said downlink shared channel signalling is provided.

(Supplementary Note 19)

A machine-type communication, ‘MTC’, device for a communication system,wherein the MTC device comprises:

-   -   means for communicating, with a communication node within a cell        operated by that communication node, using radio frames, each        radio frame comprising a sequence of subframes; means for        receiving, semi-statically, an allocation of resources for said        MTC device for use in transmitting uplink control information        relating to downlink shared channel signalling;    -   wherein said communicating means is operable:    -   to receive downlink shared channel signalling for said MTC        device in a subframe; and    -   to provide, to said communication node, using said        semi-statically allocated resources, uplink    -   control information relating to said downlink shared channel        signalling in a subframe subsequent to said subframe in which        said downlink shared channel signalling is received, wherein the        subframe in which said uplink control information is provided is        a fourth of a plurality of subframes subsequent to said subframe        in which said downlink shared channel signalling is received.

(Supplementary Note 20)

A communication node for a communication system, wherein thecommunication node comprises:

-   -   means for operating a cell; and    -   means for communicating with a plurality of different types of        communication devices within said cell using radio frames, each        radio frame comprising a sequence of subframes, wherein said        plurality of different types of communication devices include a        machine-type communication, ‘MTC’, device; and    -   wherein said communicating means is operable:    -   to provide downlink shared channel signalling for at least one        MTC device in a subframe; and    -   to receive, from the at least one MTC device, uplink control        information relating to said downlink shared channel signalling        in a subframe subsequent to said subframe in which said downlink        shared channel signalling is provided, wherein the subframe in        which said uplink control information is received is a third of        a plurality of subframes subsequent to said subframe in which        said downlink shared channel signalling is provided.

(Supplementary Note 21)

A machine-type communication, ‘MTC’, device for a communication system,wherein the MTC device comprises:

-   -   means for communicating, with a communication node within a cell        operated by that communication node, using radio frames, each        radio frame comprising a sequence of subframes; wherein said        communicating means is operable:    -   to receive downlink shared channel signalling for an MTC device        in a subframe; and    -   to provide, to said communication node, uplink control        information relating to said downlink shared channel signalling        in a subframe subsequent to said subframe in which said downlink        shared channel signalling is received, wherein the subframe in        which said uplink control information is provided is a third of        a plurality of subframes subsequent to said subframe in which        said downlink shared channel signalling is received.

(Supplementary Note 22)

A method performed by a communication node of a communication system,wherein the method comprises:

-   -   operating a cell having a cell bandwidth;    -   communicating, with a plurality of different types of        communication devices within said cell, wherein said plurality        of different types of communication devices include a reduced        bandwidth machine-type communication, ‘MTC’, device having a        bandwidth that is small compared to the cell bandwidth; and    -   allocating frequency resources respectively to each        communication device operating within said cell, for use in        transmitting uplink control data, in dependence on whether or        not that communication device is an MTC device;    -   wherein said allocating comprises allocating said frequency        resources such that:    -   when the communication device is a reduced bandwidth MTC device,        said MTC device communicates uplink control data using a first        frequency resource in a first slot of a subframe and a second        frequency resource in a second slot of that subframe wherein        said first frequency resource and said second frequency resource        share the same frequency or are separated in frequency by no        more than the bandwidth of the reduced bandwidth MTC device; and    -   when the communication device is not a reduced bandwidth MTC        device, said communication device that is not a reduced        bandwidth MTC device communicates uplink control data using a        first non-MTC frequency resource in the first slot of a subframe        and a second non-MTC frequency resource in the second slot of        that subframe wherein said first non-MTC frequency resource and        said second non-MTC frequency resource are separated in        frequency by more than the bandwidth of the reduced bandwidth        MTC device; and    -   wherein said communicating comprises receiving uplink control        information from each communication device operating within said        cell using the respective frequency resources allocated to each        communication device operating within said cell in dependence on        whether or not that communication device is an MTC device.

(Supplementary Note 23)

A method performed by a machine-type communication, ‘MTC’, device of acommunication system in which a plurality of different types ofcommunication devices can communicate with a communication node thatoperates a cell having a cell bandwidth, wherein the plurality ofdifferent types of communication devices include a reduced bandwidth MTCdevice having a bandwidth that is small compared to the cell bandwidth,wherein the method comprises: communicating with the communication nodewithin the cell operated by that communication node; and

-   -   obtaining an allocation of frequency resources, for use in        transmitting uplink control data to the communication node,        wherein said allocation is such that said communicating        communicates uplink control data using a first frequency        resource in a first slot of a subframe and a second frequency        resource in a second slot of that subframe wherein said first        frequency resource and said second frequency resource share the        same frequency or are separated in frequency by no more than the        bandwidth of a reduced bandwidth MTC device; and    -   wherein said communicating comprises transmitting uplink control        information using the allocation of frequency resources.

(Supplementary Note 24)

A method performed by a machine-type communication, ‘MTC’, device of acommunication system in which a plurality of different types ofcommunication devices can communicate with a communication node thatoperates a cell having a cell bandwidth, wherein the plurality ofdifferent types of communication devices include a reduced bandwidth MTCdevice having a bandwidth that is small compared to the cell bandwidth,wherein the method comprises: communicating with the communication nodewithin the cell operated by that communication node and using frequencyresources within a frequency of an MTC frequency band;

-   -   obtaining an allocation of frequency resources, for use in        transmitting uplink control data to the communication node        wherein said allocation is such that said communicating        communicates uplink control data using a first frequency        resource in a first slot of a subframe and a second frequency        resource in a second slot of that subframe wherein said first        frequency resource and said second frequency resource share the        same frequency or are separated in frequency by more than the        bandwidth of a reduced bandwidth MTC device;    -   moving a carrier frequency of said MTC frequency band between        said first slot and said second slot such that said MTC        frequency band includes the first frequency resource in the        first slot of the subframe and includes the second frequency        resource in the second slot of said subframe; and whereby said        communicating comprises transmitting uplink control information        using the first frequency resource in the first slot of the        subframe and transmitting uplink control information using the        second frequency resource in the second slot of said subframe.

(Supplementary Note 25)

A method performed by a communication node of a communication system,wherein the method comprises:

-   -   operating a cell; and    -   communicating with a plurality of different types of        communication devices within said cell using radio frames, each        radio frame comprising a sequence of subframes, wherein said        plurality of different types of communication devices include a        machine-type communication, ‘MTC’, device;    -   wherein said communicating comprises:    -   providing downlink control channel signalling for at least one        MTC device in a first of said subframes, and repeating said        downlink control channel signalling in at least one subsequent        subframe;    -   providing downlink shared channel signalling for said at least        one MTC device in a subframe subsequent to said subframes in        which said downlink control channel signalling is provided and        repeating said downlink shared channel signalling in at least        one subsequent subframe; and    -   receiving, from the at least one MTC device, uplink control        information relating to said downlink shared channel signalling        in a subframe subsequent to said subframes in which said        downlink shared channel signalling is provided and receiving a        repetition of said uplink control information in at least one        subsequent subframe.

(Supplementary Note 26)

A method performed by a machine-type communication, ‘MTC’, device of acommunication system, wherein the method comprises:

-   -   communicating, with a communication node within a cell operated        by that communication node, using radio frames, each radio frame        comprising a sequence of subframes;    -   wherein said communicating comprises:    -   receiving downlink control channel signalling for said MTC        device in a first of said subframes, and receiving a repetition        of said downlink control channel signalling in at least one        subsequent subframe;    -   receiving downlink shared channel signalling for said MTC device        in a subframe subsequent to said subframes in which said        downlink control channel signalling is received and a receiving        repetition of said downlink shared channel signalling in at        least one subsequent subframe; and providing, to said        communication node, uplink control information relating to said        downlink shared channel signalling in a subframe subsequent to        said subframes in which said downlink shared channel signalling        is received and repeating said uplink control information in at        least one subsequent subframe.

(Supplementary Note 27)

A method performed by a communication node of a communication system,wherein the method comprises:

-   -   operating a cell;    -   communicating with a plurality of different types of        communication devices within said cell using radio frames, each        radio frame comprising a sequence of subframes, wherein said        plurality of different types of communication devices include a        machine-type communication, ‘MTC’, device; and    -   semi-statically allocating resources to at least one MTC device        for use in transmitting uplink control information relating to        downlink shared channel signalling;    -   wherein said communicating comprises:    -   providing downlink shared channel signalling for said at least        one MTC device in a subframe; and    -   receiving from the at least one MTC device, using said        semi-statically allocated resources, uplink control information        relating to said downlink shared channel signalling in a        subframe subsequent to said subframe in which said downlink        shared channel signalling is provided, wherein the subframe in        which said uplink control information is received is a fourth of        a plurality of subframes subsequent to said subframe in which        said downlink shared channel signalling is provided.

(Supplementary Note 28)

A method performed by a machine-type communication, ‘MTC’, device of acommunication system, wherein the method comprises:

-   -   communicating, with a communication node within a cell operated        by that communication node, using radio frames, each radio frame        comprising a sequence of subframes;    -   receiving, semi-statically, an allocation of resources for said        MTC device for use in transmitting uplink control information        relating to downlink shared channel signalling;    -   wherein said communicating comprises:    -   receiving downlink shared channel signalling for said MTC device        in a subframe; and    -   to providing, to said communication node, using said        semi-statically allocated resources, uplink control information        relating to said downlink shared channel signalling in a        subframe subsequent to said subframe in which said downlink        shared channel signalling is received, wherein the subframe in        which said uplink control information is provided is a fourth of        a plurality of subframes subsequent to said subframe in which        said downlink shared channel signalling is received.

(Supplementary Note 29)

A method performed by a communication node of a communication system,wherein the method comprises:

-   -   operating a cell; and communicating with a plurality of        different types of communication devices within said cell using        radio frames, each radio frame comprising a sequence of        subframes, wherein said plurality of different types of        communication devices include a machine-type communication,        ‘MTC’, device; and    -   wherein said communicating comprises:    -   providing downlink shared channel signalling for at least one        MTC device in a subframe; and    -   receiving, from the at least one MTC device, uplink control        information relating to said downlink shared channel signalling        in a subframe subsequent to said subframe in which said downlink        shared channel signalling is provided, wherein the subframe in        which said uplink control information is received is a third of        a plurality of subframes subsequent to said subframe in which        said downlink shared channel signalling is provided.

(Supplementary Note 30)

A method performed by a machine-type communication, ‘MTC’, device of acommunication system, wherein the method comprises:

-   -   communicating, with a communication node within a cell operated        by that communication node, using radio frames, each radio frame        comprising a sequence of subframes;    -   wherein said communicating comprises:    -   receiving downlink shared channel signalling for an MTC device        in a subframe; and    -   providing, to said communication node, uplink control        information relating to said downlink shared channel signalling        in a subframe subsequent to said subframe in which said downlink        shared channel signalling is received, wherein the subframe in        which said uplink control information is provided is a third of        a plurality of subframes subsequent to said subframe in which        said downlink shared channel signalling is received.

(Supplementary Note 31)

A communication system comprising at least one communication nodeaccording to any of the supplementary notes 1 to 9, 14 to 16, 18 or 20and at least one machine-type communication, ‘MTC’, device according toany of the supplementary notes 10 to 13, 17, 19 or 21.

(Supplementary Note 32)

A computer program product comprising computer implementableinstructions for causing processing apparatus to perform the method ofany of the supplementary notes 22 to 30.

This application is based upon and claims the benefit of priority fromUnited Kingdom patent application No. 1416796.9, filed on Sep. 23, 2014,the disclosure of which is incorporated herein in its entirety byreference.

1. A communication apparatus comprising: a memory storing instructions;and at least one processor configured to process the instructions to:transmit a parameter for frequency hopping by a bandwidth limited typeuser equipment (UE), assign a frequency resource for a physical uplinkcontrol channel (PUCCH) for the bandwidth limited type UE using theparameter, wherein the parameter is different from another parameter,pusch-HoppingOffset, for frequency hopping by the non-bandwidth limitedtype UE, wherein in a first one of two consecutive slots, PUCCHtransmission is performed over a first narrowband, wherein in a secondone of the two consecutive slots, PUCCH transmission is performed over asecond narrowband.
 2. A user equipment (UE) configured to communicateusing a limited bandwidth, the UE comprising: a memory storinginstructions; and at least one processor configured to process theinstructions to: receive a parameter for frequency hopping by the UE,determine a frequency resource which is assigned for a physical uplinkcontrol channel (PUCCH) using the parameter, perform PUCCH transmissionover a first narrowband in a first one of two consecutive slots, andperform PUCCH transmission over a second narrowband in a second one ofthe two consecutive slots, wherein the parameter is different fromanother parameter, pusch-HoppingOffset, for frequency hopping by anon-bandwidth limited type UE.
 3. A method performed by a communicationapparatus, the method comprising: transmitting a parameter for frequencyhopping by a bandwidth limited type user equipment (UE); assigning afrequency resource for a physical uplink control channel (PUCCH) for thebandwidth limited type UE using the parameter, wherein the parameter isdifferent from another parameter, pusch-HoppingOffset, for frequencyhopping by the non-bandwidth limited type UE, wherein in a first one oftwo consecutive slots, PUCCH transmission is performed over a firstnarrowband, wherein in a second one of the two consecutive slots, PUCCHtransmission is performed over a second narrowband.
 4. A method for auser equipment (UE) configured to communicate using a limited bandwidth,the method comprising: receiving a parameter for frequency hopping forthe UE, determining a frequency resource which is assigned for aphysical uplink control channel (PUCCH) using the parameter; performingPUCCH transmission over a first narrowband in a first one of twoconsecutive slots; performing PUCCH transmission over a secondnarrowband in a second one of the two consecutive slots, wherein theparameter is different from another parameter, pusch-HoppingOffset, forfrequency hopping for a non-bandwidth limited type UE.